Description

Add a legacy compatible process in the addProperties function to handle the object props that contains a anonymous: true and move them to sensitiveProperties instead.

It was planned that code would use addSensistive properties, but sometimes, we get some mixed props from places like a getAnalyticsParams function that returns a lot props and passes them along far before the event is built.
It would require a too big refactoring to split these props at the source.
I decided to add a new processing in the addProperties directly to filter anonymous props passed as normal props and redirect them.

Even if this new additional processing is executed for all the addProperties calls, it is not adding enough processing time to negatively impact performances.

Related issues

Fixes #12728

Manual testing steps

1. View the tx approval screen
2. check Approval Started event props
3. generates both a non-anonymous and an anonymous event.
4. Only anonymous event contains number_tokens_requested

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.